The World of Computer Software/The World of Computer Software.iso/zl2b0115.zip/BETA.HST

Text File | 1993-01-15 | 26KB | 572 lines

ZipLab Plus 2.ß (BETA)
Beta version history file


IF THIS IS THE FIRST VERSION OF ZIPLAB 2.0 BETA WHICH YOU ARE TRYING, DON'T
EVEN BOTHER WITH THIS FILE.  JUST READ AND FOLLOW THE DIRECTIONS IN THE
FILE "ZIPLAB.DOC".


2.ß.8 - January 15, 1992
************************

Please replace the following files with the new ones from this archive:

ZLAB.EXE
ZSET.EXE
ZIPLAB.DOC
BETA.HST
CFGCVT.EXE

NOTE! Your ZLABxxx.CFG files are going to be changed for this version.  The
changes will encorporate all modificatios to the .CFG files to date, and
you will be able to upgrade from any previous 2.0 beta version in one
step.  Do read all change history entries for any versions which you have
not yet implemented, as the defaults set by CFGCVT.EXE may not fit your
system or your requirements.

Please run the enclosed CFGCVT.EXE for each of your .CFG files, with the
name of the ZLABxxx.CFG file as the only parameter.  This will convert your
configuration files to the latest format.  Then use ZSET to modify for your
system and requirements.

1)  Added the ability to use the "virus checking" program of your choice.
    To do this, I have allowed changes to 1 line (*), and added 2 lines
    to the ZLABxxx.CFG file format:

                     2
                     The Interconnect Bulletin Board System
                     C:\FAIL
                     C:\ZIPLAB\ZLAB000.TCN
                     199001
                     Y
                     Y
                     Y
                     Y
                     Y
                     C:\ZIPLAB\
                     C:\ZIPLAB\ZLAB000.CMT
                     Y
                     NONE
                     C:\UTILITY\PKZIP.EXE
                     -) -- -+ -3 -~ -(
                     C:\UTILITY\PKUNZIP.EXE
                     -) -- -+ -3
                     C:\UTILITY\LHA.EXE
                     C:\UTILITY\ARJ.EXE
                     C:\UTILITY\TDCHECK.EXE
               * >>  C:\UTILITY\SCAN.EXE
               1 >>  /NOMEM /NOBREAK /NOEXPIRE /NOPAUSE
               2 >>  1
                     C:\UTILITY\RECOM.EXE
                     C:\UTILITY\DELF.COM
                     C:\UTILITY\GIFTEST.EXE
                     /B:2 /F:UPDESC.2
                     GIF;EXE;PCX
                     C:\ZIPLAB\CRC.ADS
                     C:\ZIPLAB\LST.ADS

     * - Full DRIVE:\PATH\FILENAME.EXE of the virus checker to use.  NOTE!
         be sure that this is an appropriate program!  It must have
         reasonable memory requirements, allow for completely automatic
         command-line driven use, and return an ERRORLEVEL on detection
         of a virus.  I have tested SCAN.EXE and F-PROT.EXE, and feel
         confident that either of those two will do the job correctly.
         I will not however, worry myself in the slightest if you use
         another program and have problems.  I just can't support every
         possible virus checker out there.  If you have problems, I will
         simply tell you to go back to SCAN and see if that fixes it.

     1 - Optional command line switches to pass to the virus checker.  Be
         sure you have read the docs for the program you use.  As with
         the program in general, I only warrent that the switches I have
         used as an example for SCAN will work correctly.  If you decide
         to use something else, be sure you understand and have tested
         any switches you provide.  I do feel confident that these work:

         SCAN         /NOMEM /NOBREAK /NOEXPIRE /NOPAUS
         F-PROT       /NOMEM /NOBREAK /OLD

         Do NOT set a switch which causes the virus checking program
         to delete or rename the file.  ZipLab will take care of that.

     2 - The DOS ERRORLEVEL which is set by the program if a file virus
         is detected.  This can only be ONE number, and unlike DOS, it
         is not a function of "less than this number".  It is EXACTLY
         this number.  Again, I have tested this with SCAN and F-PROT,
         but have no idea if any other virus checkers return appropriate
         ERRORLEVELs.  The ERRORLEVELS set on virus detection for the two
         that I do know are:

         SCAN         1
         F-PROT       3

         I do not use NAV or CPAV here, and have no way of knowing if they
         are appropriate for ZipLab or not.  If you are successful in
         getting either of these two "mainstream" products to work, feel
         free to pass along the settings in a message (the RIME ZipLab
         conference would be a good place), so others may benefit.


OUTSTANDING CURRENT ITEMS:  These items will be in 2.0 at some point.

* LST.ADS processing WAAAAY too slow, and 100 is the limit..
* Don't check "bbs ads" on date limit validation (it does now...)
* A version of ZCRC.EXE which accepts DOS "wildcards"
* Allow one "user defined" function in ZipLab.
* Word wrapping on incorrectly formatted .DIZ files.

OUTSTANDING FUTURE ITEMS:  These requests may or may not make version 2.0

* FOSSIL driver routines - researching...
* List of users to exempt from testing - Why?
* Have files failed for AGE or TCAN put
  in the .TCN file so they won't be
  uploaded again. - Maybe...
* ANSI autodetect
* Non-graphic option/version. - Not likely
* Add -AV information to the description

OTHER OUTSTANDING ITEMS:
* Generic version - next major effort
* WildCat! version - after generic


2.ß.7 - January 12, 1992
************************

Replace only the ZLAB.EXE and BETA.HST files for this release.  All others
are unchanged from 01/11/93 - 1st or 2nd daily.  Your .CFG files are
unchanged.  This version was popped out quick to correct some serious
problems with ProDoor (or as John Friel says, "way cool FUBARs").  Another
release is quite likely later this evening.

1)  Additional work was done on ProDoor, to correct a problem when a file
    failed the test.  ZipLab was either aborting with an ERROR 62, or was
    in some cases causing a hang with a "string space corrupt" error.  I
    hope that this is now fixed.  Beat it up and let me know.

2)  ZipLab was not properly handling "unannounced" uploads to ProDoor.  It
    assumed that $DOOR.NAM existed, and that all files to be tested were
    in it.  Fixed...


2.ß.6 - January 11, 1992 - 2nd daily release
********************************************


Replace only the ZLAB.EXE and BETA.HST files for this release.  All others
are unchanged from 01/11/93 - 1st daily.  Your .CFG files are unchanged.


1)  Problems with ProDoor and the description handling have been addressed.
    Please let me know if there are futher problems.

    NOTE!  You must be running ProDoor 3.44 or better, and MUST have a
    PCBOARD.DAT AND PCBOARD.SYS configuration which matches the 14.5a
    version of PCBoard.  At least one sysop tells me he is running ProDoor
    with 14.0 versions of PCBOARD.SYS/DAT.  THIS WILL NOT WORK.

2)  Further work done on GIFTEST routines.  It works here just fine now,
    and inserts resolutions in both PCBoard and ProDoor descriptions.  If
    It doesn't work for you, PLEASE READ THE DOCS FOR GIFTEST CAREFULLY!
    I have found that you MUST specify /B:2/N:2/F:UPDESC.2 as the command
    line for GIFTEST for it to work correctly with the descriptions.  You
    should replace the "2's" in the parameters above with appropriate ones
    for your system.  I have tested ZipLab with the 4.0ß (8/25/92) version
    of GIFTEST.  I have no idea if anything has changed in any later
    releases.  Dave Navarro - Can I get the latest from you?

3)  Files which fail .TCN (Trashcan) testing when in TEST mode were being
    moved offline... Fixed.

4)  No mail messages will be sent from SYSOP to SYSOP on test failure,
    unless the failure is due to virus detection.

5)  Problems with people putting blank lines at the top or bottom of the
    ZLABxxx.CFG files has been fixed.  It will still abort if you have
    an invalid .CFG file, but at least it will tell you why.

6)  An improperly formatted FILE_ID.DIZ file (lines longer than 45 chars),
    was messing up the DIRxx files.  The lines will be truncated for the
    time being, with a word-wrap routine in the works for a future beta.

7)  The problem encountered if your PCB "home" directory was a ROOT dir
    has been fixed.

8)  The path was being added along with the filename in .ARJ files if you
    elected to add a file to the archive.  Fixed.

9)  The parameters for PKUNZIP which I added in 01/11/93 - 1st daily were
    not being parsed properly.  They were not being implemented when
    PKUNZIP was run.  Fixed.



2.ß.5 - January 11, 1992 - 1st daily release
********************************************

Replace the following files with the versions in this archive.  All others
are unchanged from 01/03/93.

ZSET.EXE
CFGCVT.EXE
ZLAB.EXE
BETA.HST
ZIPLAB.DOC

1) The configuration files have changed.  I have included a small utility
   called CFGCVT.EXE in the archive, which can be used to convert your
   ZLABxxx.CFG files from the January 1-3 versions to this one.  If you
   are still running the 12/28/92 version, you must reconfigure from
   scratch.

   Just run:

   CFGCVT [drive:][\path\]ZLABxxx.CFG

   In about a heartbeat, it will come back and tell you that it has
   converted the file.  You may NOT run CFGCVT.EXE on a single .CFG
   more than once, and once you have converted all your .CFG file you
   may safely just erase CFGCVT.EXE.  A new version will ship with any
   future beta's which require .CFG modifications.

   All of your modifications will survive the change, with 2 new lines
   being added to the .CFG file:

                     2
                     The Interconnect Bulletin Board System
                     C:\FAIL
                     C:\ZIPLAB\ZLAB000.TCN
                     199001
                     Y
                     Y
                     Y
                     Y
                     Y
                     C:\ZIPLAB\
                     C:\ZIPLAB\ZLAB000.CMT
                     Y
                     NONE
                     C:\UTILITY\PKZIP.EXE
              1 >>   -) -- -+ -3 -~ -(
                     C:\UTILITY\PKUNZIP.EXE
              2 >>   -) -- -+ -3
                     C:\UTILITY\LHA.EXE
                     C:\UTILITY\ARJ.EXE
                     C:\UTILITY\TDCHECK.EXE
                     C:\UTILITY\SCAN.EXE
                     C:\UTILITY\RECOM.EXE
                     C:\UTILITY\DELF.COM
                     C:\UTILITY\GIFTEST.EXE
                     /B:2 /F:UPDESC.2
                     GIF;EXE;PCX
                     C:\ZIPLAB\CRC.ADS
                     C:\ZIPLAB\LST.ADS

     1  -  An optional list of extra parameters you wish to pass to
           PKZIP.EXE on the command line.  I will pass these JUST as
           you type them, so be sure you have read the documentation
           (MANUAL.DOC and ADDENDUM.DOC) that comes with PKZIP.  This
           was added primarily due to some problems with the "advanced"
           features of PKZip 2.0.  I strongly suggest that you use
           the command line parameter additions as suggested above.
           They do the following:

           -)     Turn off DMPI memory usage
           --     Turn off XMS memory usage
           -+     Turn off EMS memory usage
           -3     Turn off 386cpu specific code
           -~     Turn off NETWORK specific code
           -(     Uses slower form of memory handling

           "NONE" will cause ZipLab not to pass any extra parameters.

NOTE!!!!   DO *NOT* PASS THE PRIMARY COMMAND (like -a or -d) FOR PKZIP,
           ONLY EXTRA "SWITCHES" WHICH MODIFIY HOW PKZIP OPERATES.
           ZIPLAB WILL PASS THE PRIMARY COMMAND PARAMETER IT NEEDS FOR
           A PARTICULAR FUNCTION.

     2  -  An optional list of extra parameters you wish to pass to
           PKUNZIP.EXE on the command line.  It is strongly recommended
           that you use the parameters in the example above. They do the
           following:

           -)     Turn off DMPI memory usage
           --     Turn off XMS memory usage
           -+     Turn off EMS memory usage
           -3     Turn off 386cpu specific code

           Please note that -~ and -( are valid switches for PKZIP.EXE
           ONLY, and will cause PKUNZIP.EXE to return an error.

           "NONE" will cause ZipLab not to pass any extra parameters.

NOTE!!!!   DO *NOT* PASS THE PRIMARY COMMAND (like -x or -v) FOR PKUNZIP,
           ONLY EXTRA "SWITCHES" WHICH MODIFIY HOW PKZIP OPERATES.
           ZIPLAB WILL PASS THE PRIMARY COMMAND PARAMETER IT NEEDS FOR
           A PARTICULAR FUNCTION.

     3  -  There was a problem where ZipLab was not recognizing the word
           NONE on the line for a custom comment to add to the .ZIP.
           Fixed.

OUTSTANDING CURRENT ITEMS:

* Further ProDoor work needed
* Further GIFTEST work needed
* Don't check "bbs ads" on date limit validation (it does now...)
* ANSI autodetect
* Allow other virus check programs than just SCAN
* LST.ADS processing WAAAAY too slow, and 100 is the limit..
* A version of ZCRC.EXE which accepts DOS "wildcards"
* Allow one "user defined" function in ZipLab.
* TCAN (.TCN) hit being moved offline in TEST mode.  Shouldn't.
* Messages being sent to SYSOP on his own upload failures.  Pointless..
* Word wrapping on incorrectly formatted .DIZ files.
* Problem if the PCB "home" directory is a ROOT directory of a drive.
* Blank lines at top or bottom of ZLABxxx.CFG file causing problems.

OUTSTANDING FUTURE ITEMS:

* FOSSIL driver routines
* List of users to exempt from testing
* Non-graphic option/version.
* WildCat! version
* Generic version


2.ß.4 - January 3, 1992
*************************

Just a documentation change so far today.  I wanted to add some stuff
about GIFTEST -  These additions have been added to ZIPLAB.DOC.

IV.  Using GIFTEST with ZipLab

ZipLab does not pass any default parameters at all to Giftest.Exe.  You
will need to do that by specifing the parameters on the line in
ZLAB000.CFG which is for this purpose.  If all you want to do is test .GIF
files for integrity, and make sure they pass some standard of resolution
and colors that you set, This is all pretty easy.  Just use:

/M:640X480X256     (replace the resolution and colors with yours)

Giftest will work just fine with a simple parameter line like this. If you
want to insert the resolution/colors into the PCBoard description, it gets
a bit tricky... The first thing you have to tell Giftest is what board
type you are running, so follow the parms above (no spaces) with:

/B:x   (Where "x" is a "1" for ProDoor or a "2" for PCBoard)

Now we need to tell Giftest where the description file is for the node you
are on.  This is the tricky part... To do this, you are GOING TO HAVE TO
HAVE A DIFFERENT ZLAB000.CFG FILE FOR EACH NODE. Follow the parms above
(no spaces) with:

/F:drive:\path\description.file

Now in PCBoard, that is going to be the drive and directory which is
specified on line 179 of PCBoard.Dat, and then the filename of UPDESC.x
where "x" is replaced with the node number for the current node.  (just
use UPDESC without an extension if you are not running nodes)

In Prodoor, the path will be your PCB home directory FOR THAT NODE, and
the filename will be $DOOR.NAM.

Please do not use the "/E" parameter on the Giftest parameter line. ZipLab
will take care of the file if it fails, there is no need to have Giftest
erase the file, and it will only confuse ZipLab.

You will then have to do this for each node you have, and they will have
to be in different directories.  I recommend that you use something like
C:\ZIPLAB\NODE1 as a directory to hold your node 1 .CFG files.  All the
other files for ZipLab with the exception of the ZLABxxx.CFG files can
still be shared and can reside in C:\ZIPLAB or wherever you have specified
in the .CFG files.

                                                                         Pg14
Then change your ZLAB command line in PCBTEST.BAT to something this for
node 1:

PCBoard:
ZLAB %1 %PCBDRIVE%%PCBDIR% C:\ZIPLAB\NODE1 %2

ProDoor:
ZLAB %TARGET% %pcbdrive%%pcbdir% C:\ZIPLAB\NODE1

The other option is to put the ZLABxxx.CFG files in the home PCB directory
for each node, and then the command line is simple:

PCBoard:
ZLAB %1 %PCBDRIVE%%PCBDIR% %PCBDRIVE%%PCBDIR% %2

ProDoor:
ZLAB %TARGET% %pcbdrive%%pcbdir% %pcbdrive%%pcbdir%


2.ß.3 - January 2, 1992
*************************

Just a quick fix for the .GIF testing routines, which were going off
into a "loop" if the .GIF failed testing on some systems.  No changes
required to any .CFG or other files.  Just drop in the .EXE


2.ß.2 - January 1, 1992
*************************


1)  4 new lines added to the .CFG file:  If you are running a version
    older than January 1, you MUST recreate your .CFG files from scratch.

                     2
                     The Interconnect Bulletin Board System
                     C:\FAIL
                     C:\ZIPLAB\ZLAB000.TCN
                     199001
                     Y
                     Y
                     Y
               1 >>  Y
               2 >>  Y
               3 >>  C:\ZIPLAB\
                     C:\ZIPLAB\ZLAB000.CMT
               4 >>  Y
                     NONE
                     C:\UTILITY\PKZIP.EXE
                     C:\UTILITY\PKUNZIP.EXE
                     C:\UTILITY\LHA.EXE
                     C:\UTILITY\ARJ.EXE
                     C:\UTILITY\TDCHECK.EXE
                     C:\UTILITY\SCAN.EXE
                     C:\UTILITY\RECOM.EXE
                     C:\UTILITY\DELF.COM
                     C:\UTILITY\GIFTEST.EXE
                     /B:2 /F:UPDESC.2
                     GIF;EXE;PCX
                     C:\ZIPLAB\CRC.ADS
                     C:\ZIPLAB\LST.ADS


     1  -  A "Y" if you wish ZipLab to send a mail message to the user
           when a file fails testing.  A "N" if not.
           DEFAULT = Y

     2  -  A "Y" if you wish the sysop to also receive a mail message in
           the instance of a virus detection.  A "N" if you do not.
           DEFAULT = Y

     3  -  The DRIVE\PATH\ to the directory which will hold the .MSG files.
           These are the mail messages sent to the user/sysop on failure.
           Please put a "\" at the end of the path.
           DEFAULT = C:\ZIPLAB\

     4  -  A "Y" if ZipLab should add the contents of FILE_ID.DIZ (if
           found) to the bottom of the zip comment.  "N" to disable.
           DEFAULT = Y

2)  I have finished the routines to send mail messages in PCBoard/Prodoor
    to the user/sysop if a file fails.  This is an optional item, with the
    enable/disable of the feature set in ZLABxxx.CFG in 2 of the new lines.

    There are sample text files included in the archive.  These files are
    the ones which will be sent as a PCB/Prodoor mail message to the
    user (and Sysop as well in the case of a virus).

    The files (and failure reasons) that ZipLab Plus uses are:

    NAME OF FILE      REASON FOR FAILURE
    ------------      ------------------
    OLDDATE.MSG       Failed date limit checking
    FILECRC.MSG       Failed CRC or -AV checking
    IMBEDCRC.MSG      An imbedded archive failed CRC or -AV checking
    TRASHCAN.MSG      .TCN (Trashcan) text was found in the description
    BADTD0.MSG        A Teledisk format (.TD0) file failed TDCHECK
    USRVIRUS.MSG      Message sent to USER on virus detection
    SYSVIRUS.MSG      Message sent to SYSOP on virus detection
    UNACCEPT.MSG      An unaccepted file format was uploaded
    GIFFAIL.MSG       A .GIF file failed GIFTEST

    These files may NOT be renamed from the sample ones I sent in the
    archive, but may be modified to contain any text you want.  You
    may also use the @ZCODES (see ZIPLAB.DOC) in the text, including
    one new @ZCODE described below.

    You must also tell ZipLab where the files are located, in the line
    which is indicated with a "3 -" above.  Only the path please, and
    follow the path with the "\" character.  I strongly suggest that you
    just put these in your C:\ZIPLAB\ directory along with the .TCN,
    .CMT, ADS.CRC and LST.CRC.

    A sample message file, OLDDATE.MSG:

    // MESSAGE FROM ZIPLAB PLUS @V_N@

    On @D_T@ at @T_T@ you uploaded:

    @F_N@

    This file failed ZipLab Plus upload testing.
    The reason for failure was:

    Date limit failure - Files are older than acceptable limit.

    This BBS only accepts programs and files created on @D_L@ or later.
    The newest file in this upload was dated @N_F@.  Please check the
    dates of the files inside an archive before uploading.

    // AUTOMATED MESSAGE FROM ZIPLAB PLUS
    // PLEASE DO NOT REPLY TO THIS MESSAGE

    If you want to send messages for some types of failures and not
    for others, just rename or delete the appropriate file.  If
    ZipLab doesn't find a .MSG file for the failure reason in question,
    it will just go on without sending anything.

3)  As requested, I have allowed a "Y" or "N" toggle in the .CFG file
    to tell ZipLab whether or not to append the contents of FILE_ID.DIZ
    (if found) to the bottom of the Zip "comment".  A "Y" will enable
    the append, a "N" will disable it.

4)  The word ONLINE will no longer appear after the user name on the
    local screen.  This was a bit obvious and cluttered up the
    screen for no good reason.  The OFFLINE and OFFLINE-OFFHOOK
    messages will still appear to let you know the user has hung up,
    and that ZipLab has taken the phone line offhook (busy) during
    testing.

5)  I have added a new @ZCODE:  @T_C_T@  This is "Trash Can Text" and
    will contain the keyword or phrase which was matched on a file
    reject due to .TCN match.  This can be used in both the .CMT and
    the new .MSG files, along with the original @ZCODES.

6)  Several minor cosmetic or technical fixes, with no impact on you.

7)  Full ZIPLAB.DOC documentation updated to reflect the changes in
    this beta.

OUTSTANDING CURRENT ITEMS:

* FOSSIL driver routines
* Don't check "bbs ads" on date limit validation (it does now...)
* ANSI autodetect
* Allow other virus check programs than just SCAN
* LST.ADS processing WAAAAY too slow
* A version of ZCRC.EXE which accepts DOS "wildcards"

OUTSTANDING FUTURE ITEMS:

* WildCat! version
* Generic version


2.ß.1 - December 28, 1992
*************************

First beta version - Missing the feature of sending a mail message to
the user and sysop on virus detection.  This feature in development.